Proposed changes

When loading a config and result is falsy, set empty config for result.

fixes #26

Types of changes

What types of changes does your code introduce
Put an x in the boxes that apply

• Bug (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature which changes existing functionality)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING guide
• Lint and unit tests pass with my changes
• I have added tests that prove my fix is effective/works
• I have added necessary documentation (if appropriate)
• Any dependent changes are merged and published in downstream modules

Further comments

Do you have any suggestions on how to add a test for this? cosmiconfig searches the file tree, and there is a config in the file tree, so, I wasn't sure the best approach to write a test that does not have a config? I will think a little longer on it, but wanted to get the PR open and see if anyone had suggestions.

I did not see a CONTRIBUTING.md file or contributing guidelines in this repo, so I did the best I could to follow what I believe would be expected. Let me know if I missed anything.

Reviewers: @michael-ciniawsky, @ertrzyiks